Inventory Options

Controls the number of decimal digits for all pricing fields including sales, purchasing, inventory values, job costs, etc.

• Final dollar values that appear on Sales and Purchase Orders will be rounded to the normal two decimal places.

Controls the number of decimal digits for Bill of Materials(BOM) quantities used for production and sales. Allowed range is 0-10.

Controls the number of decimal digits, between 0-9, displayed in MRP results.

• Truncated decimals are rounded up.

Pick list used when producing assemblies that specifies how the cost should be allocated in Average or FIFO / Actual "Inventory Costing" modes. Options are:

• Quantity - The cost of each item produced is the total cost of all material being relieved divided by the total quantity of items produced.
  • This option can produce undesirable Lot values when producing different types of items at the same time.
• Standard Cost - The cost of each item produced is the total cost of all material being relieved, multiplied by the standard cost of the item produced, and divided by the standard cost of all materials being produced.
  • Requires that "Acct. Std." fields be populated on the Item Master Costs tab, even though they would not otherwise be used in Average or FIFO / Actual Inventory Costing modes.
• Volume - The cost of each item produced is the total cost of all material being relieved, multiplied by the Unit Volume of the item produced, and divided by the total volume of all materials being produced.
  • Requires that "Unit Volume" field be populated on the Item Master Calcs tab.
• Weight - The cost of each item produced is the total cost of all material being relieved, multiplied by the Unit Weight of the item produced, and divided by the total weight of all materials being produced.
  • Requires that "Unit Weight" field be populated on the Item Master Calcs tab.

Pick list used to set the default behavior for generating serial numbers, when Parts flagged as "Unit Serialization" on their Item Master Properties tab are produced. Options are:

• Manual - Each serial number must be manually entered.
• Sequential - Each serial number is generated sequentially.
• User-Defined - Each serial number is generated according to the "Unit Serial # Expression" entered.

Memo field used to define the serial number expression to be used when "Unit Serial # Generation" is set to "User-Defined".

• The available fields for use in this text are:
  • ln_Serial, all Item Master fields, including User Fields, attrib1, attrib2, attrib3, codenum, descrip, id, parented, qcstatus, userlot, serial.
• User-defined counters may be set in this field. To support this, the "In_Allonum" is available, representing the current transaction number (Job, PO, SO) and the INCREMENT function is available to all calcs.
• The signature of the INCREMENT is: "INCREMENT (counter_name [, counter_digits = 5])" where counter_name is required and counter_digits is optional and defaults to 5.
• Example: ALLT (IIF (BETWEEN (ln_Allonum, 100000000, 999999999) AND pr_level = 50, TRANS (ln_Allonum, "9999-99999") + "-" + ALLT (STR (INCREMENT (TRANS (ln_Allonum, "9999-99999"), 6), 9, 0)), STR (ln_Serial, 9, 0))), which evaluates as follows: If Job number is valid and Item Type is Finished Good, then the system will use the Job Number + a dash (-) + counter seeded off Job Number (6 digits), otherwise use the default Deacom Serial Number -- trimmed. With this serial number calculation, finishing a Finished Good on a Job yields serial numbers like 2014-00001-1, 2014-00001-2, 2014-00001-3, etc. Serial numbers from any other receipt are just the base number.

Pick list used to set the default behavior for generating container serial numbers, when Parts flagged as "Container Serialization" on their Item Master Properties tab are produced. Options are:

• Manual - Each container serial number must be manually entered.
• User-Defined - Each container serial number is generated according to the "Cont Serial # Generation" entered.

Memo field used to define the container serial number expression to be used when "Cont Serial # Generation" is set to "User-Defined".

Pick list used to determine how master lot numbers will be generated. Options are Sequential, Manual, and User Defined.

• Sequential - Master lot numbers will automatically be generated sequentially by the system.
• Manual - Users will need to enter master lot numbers when creating master lots in the system.
• User-Defined - The system will evaluate the expression in the "Master Lot Expression" field and use that to generate the master lot number. In this case, users will not be able to modify the number when new master lots are created.

Text field used to define how master lot numbers will be generated when using the "User-Defined" option in the Master Lot # Generation field.

• The following fields are available to this expression:
  • All fields in the sales order header (dttord) table, including sales order user fields and user calculations.
  • System constants.
  • All fields in the job header (dtjob) and job lines (dtljob) table including job user fields and job user calculations as well as all fields in the inventory-in (dtfifo) table. Notes: 1. The fields referenced in this bullet point are available to the expression when creating a master lot through the input production or the close/relieve forms, in both the main and WMS applications. The fields will return a null value in the expression when a master lot is being created outside of a job. 2. The dtfifo fields will come from the lot being produced. 3. In order to use a user field or user calculation in the expression, the name of the calculation or user field must be referenced in the expression.
  • All Bill-to fields (dmbill) and Bill-to user fields when finishing a job from the Input Production form.

Memo field used to store an expression that automatically generates User Lot numbers when material is finished on a Job.

• If this field is left blank, the system will use the production Job number as the User Lot number.
• For the information and values within this field to be displayed on Report Layouts and Part Forms, the "fi_userlot" field name must be added to the appropriate Job reports.
• The available fields for use in this text are:
  • Job header fields (jo_*) including Job header date fields and User Fields
  • All Item Master fields including User Fields, all of which must be preceded by cPROD, i.e. cPROD.pr_shelf
  • dtljob.*, waid, jo_closed, pr_codenum, pr_descrip, pr_loid, pr_invchid, pr_control, pr_stocked, pr_finwip, pr_finpart, pr_finmat, pr_finlab, pr_finbur, pr_matexp, pr_catch, pr_ordtype, pr_backjob, pr_unid, pr_prunid, pr_unitwgt, pr_unitvol, pr_unitcub, pr_unitlen, userlot, attrib1, attrib2, attrib3, tally, tallydesc, partnum, prfact, start, finish, quant, leftover, loid
• When using date fields in an expression, use DTOC (i.e. DTOC(jo_*)) to display dates as MM/DD/YYYY or DTOS (i.e. DTOS(jo_*)) to display dates as YYYY/MM/DD.

CHILDLOT function - This function works in conjunction with the "Propagate User Lot" flag on the Edit BOM Line form when editing a Bill Of Materials. The purpose of this feature is to allow the User Lot number from the bulk material used in production to carry over to the Finished Good when finishing production.

• Example: Assume there is a Finished Good of a 5 gallon can of paint. The BOM for this 5 gallon can of paint includes the can, lid, label and finally, the paint itself, which is the bulk material. Assume the User Lot of the paint which was consumed in the production process (either via issuing or backflushing) should carry over to the final product, namely the 5 gallon of paint.
• To accomplish this, the "Propagate User Lot" flag must be checked on the bulk material (paint) on the BOM for the Finished Good (5 gallon can of paint) and at a minimum "CHILDLOT()" needs to be added to this field. Additional fields and/or expressions can be used within the brackets of the CHILDLOT() statement. Note that simply checking the "Propagate User Lot" flag will not propagate the bulk material user lot number to the finished good user lot number. For the process to work, the CHILDLOT() function must be used in the Lot # Expression field.
• When quantities of the Finished Good are produced and placed into inventory or QC, the User Lot number of the finished Lot will be the same as the User Lot number of the bulk material that was consumed by or issued to the Job.
• This function is designed to be used in situations where bulk materials or subassemblies are made on separate Jobs then the Finished Goods. In this way, the bulk material or subassembly will already be available in inventory with a Lot number. When this Lot is issued to the Finished Good Job or a Lot is consumed, via backflushing, to the Finished Good Job, then the Lot number will be carried over to the finished goods that are placed in inventory.

Memo field used to store an expression that generates expiration dates when finishing lots.

• If this field is left blank, the system will use standard expiration determination based on how the lot is finished/produced and placed into inventory:
  • The date specified in the "Expires" field on the Close/Relieve Job form for the job line or the "Expires" field on the Input Production form, or
  • The expiration date for a raw material or component that goes into the item lot being finished is the "Propagate Expiration Date" flag is checked on the specified raw material of component, or
  • Date that lot is finished plus the shelf life date specified on the Item master record.
• The available fields for use in this text are all the Job header date fields and the Item Master "Shelf Life Days" (pr_shelf) field.
• Two variables can be used in this field:
  • relievedexpires - this should be the oldest fi_expires date of the lot that is relieved for the BOM line that has the "Propagate Expiration Date" (bo_useexp) set to TRUE.
  • relievedlotdate - this should be the oldest fi_lotdate of the lot that is relieved for the BOM line that has the "Propagate Expiration Date" (bo_useexp) set to TRUE.
  • Business Case: - these two variables support the ability to determine the expiration date of finished goods when both the finished good and supporting sub assemblies have different self life and the "Propagate Expiration Date" will normally only bring over the shelf life/expiration date for the sub assembly. For example, assume a sub-assembly has a shelf life of 60 days, but the finished good has a shelf life of 6 months. Using only the "Propagate Expiration Date" from the sub assembly does not factor in the 6 month shelf life set on the finished good. Note: In the case where no BOM lines have bo_useexp set to True, these variables will return empty.

Text field used to modify how BOM attributes are propogated. When not empty, the constraint in Bills of Material which only allows one line to have "Propagate Attribute" will be disabled, allowing multiple mulines to have this flag checked.

• When propagating attributes, the values of this field will be taken between the attribute delimiter, trimmed, then propagated separate by the delimiter again.

If checked, forms used to finish material on a Job will provide a preview of the Lot number, generated using the defined "Lot # Expression", prior to the finishing process being completed.

• If not checked, the word "System" will be displayed in forms as the Lot number until the finishing process is complete, then a Lot number will be generated.
• Unchecking the flag is useful in situations when using a Lot expression with a function, such as INCREMENT(), and users may need to modify or open the Close/Relieve Job form multiple times prior to actually finishing. To further illustrate, if users have the expression ""Test" + '-' + ALLT(STR(INCREMENT("test"),10))" in the "Lot # Expression" field and access the Close/Relieve Job multiple times without finishing, users will notice that the Lot number is being incremented by 1 each time the form is opened.

Stores the calculations used to determine the "Load 1-3" field values on the Item Master Costs 2 tab.

• Load costs are ways of tracking additional expenses and do not affect the general ledger.

Pick list used to set the default selection for the field of the same name on the Edit Bill of Materials form, which indicates how Batch Yields are calculated.

Pick list used to set the default selection for the "BOM Type" field on the View Bill of Material form, which determines how the BOM is displayed.

Sets a pre-defined Time-Phased MRP pre-filter template to be used when MRP reports are generated via the "BOM MRP" button when viewing BOMs.

• Pre-filter templates are created using the "Settings" button on the pre-filter with all desired fields completed.
• The pre-filter template must be saved for "All Users".
• If no selection is made in this field, the system will run an Instant MRP report.

If checked, the system will include the quantities of BOM lines with the "By-Product" flag checked in the Batch Yield calculation.

If checked, the system will include Co-Product lines in the BOM\Item cost roll up. Defaults to False.

If checked, UPC numbers must be unique and UPC numbers cannot be used between different parts. This field is checked by default.

• In the WMS application, where the same UPC number is used on multiple items, the system will display a form with the part numbers associated with the scanned UPC and allow the user to select which part number they would like to use.
• One reason to have this field unchecked is the situation where manufactures reuse UPC codes from discontinued items.

If checked, the "Retain Current Location" flag on the Issue/Reserve Inventory form will be checked by default when issuing material in the main application and in WMS.

• Applies regardless of option selected in the "Type" field on the Issue/Reserve Inventory form.

All reserved sales orders need to be created with a Master lot. Defaults to false. The field will drive whether or not the Make Master lot flag on the reserving form in the WMS is checked by default when the form is loaded. This option is useful in situations where the majority of reserved sales orders need to be created with a master lot in Deacom. An example might be situations where the standard order is a tractor trailer load.

If checked, users must enter a weight when creating Master Lots in the system, including in WMS.

If checked, the default catch weight value will be set to zero when using the Input Production or Purchasing > Receive transactions in both the main and WMS applications.

• If not checked, the default catch weight will be taken from the "Unit Weight" specified on the Item Master Calcs tab.

Pick list used to determine the sort order for information on the Pre-Staging Picking List. Options are:

• BOM Sequence
• Line
• Location
• Location Type - The system will sort by Location Type name, then Location name, on pick lists.
• Part Number
• Total Weight

Defines the default quantity when final staging in the main application as well as the WMS application. Options are Full or Zero. Full is the default.

Pick list used to determine the sort order for information on the Final Staging Picking List. Options are:

• BOM Sequence
• Line
• Location
• Location Type - The system will sort by Location Type name, then Location name, on pick lists.
• Part Number
• Total Weight

Pick list used to determine if System Lots within the same User Lot may be substituted when Final Staging for Jobs or Sales Orders. Options are:

• None - System Lot substitutions are not allowed during Final Staging.
• System Lot - Allows any System Lot to be used, as long as:
  • The new System Lot is within the User Lot of the original System Lot selected.
  • The quantity in the new System Lot has enough to satisfy the original System Lot's quantity.
  • The new System Lot is in an appropriate status - i.e. it has passed any necessary QC tests and is in an inventory segment other than WIP, Quarantine, or In Transit.

Pick list used to set the default selection for the "Inventory" field on the Pre-Staging form, which determines which Lots are available to pre-stage.

Supports the Staging Across Facilities feature in Deacom. Options are:

• All - Displays all Lots.
• Facility - Displays Lots in the same Facility as selected on the Job/Sales Order. This is the default selection.
• Facility Group - Displays Lots in the same Facility Group as the Facility selected on the Job/Sales Order.

This will sort the orders based off the SO Sort expressions in this memo box if desired (Group / Sort is flagged on the Inventory - Pre-Staging form).

This will group the orders based off the SO Group expressions in this memo box if desired (Group / Sort is flagged on the Inventory - Pre-Staging form).

If checked, will enable the “Scan Parts” flag on the Inventory Final Staging form in the main application and WMS by default.

If checked, will remove the excess pre-staged quantity after a Part is final staged and placed back into inventory.

• Due to the potential for some minimal material losses during the weigh-up process, checking this flag is a recommended best practice.

If checked, indicates the system will attempt to read weight values from the scale attached to the system by default.

If checked, the "Print Master Lot Label" flag on the Staging" Inventory Final Staging form is checked by default in the main application.

If checked, when final staging to a Job that contains a Part with a Formula that contains the same Part on multiple lines, the staging function will lump all required quantity for the Part from all BOM lines into one staging transaction.

• If not checked, when a Job and Part are selected on the Inventory Final Staging form and the Part on the Job contains a Formula that contains the same Part on multiple lines, a "BOM Sequence" field will appear, allowing the user to select which BOM Sequence they wish to stage for the selected Part.
• Example: Assume there is a Part called FINI1, which has a Formula with three lines: Line 1 is for Part Raw1 and quantity 5, Line 2 is for Part Sub1 and quantity 1, Line 3 is for Part Raw1 (same Part as Line 1) and quantity 2. If this flag is not checked, when a user attempts to final stage to a Job containing FINI1 and selects the Raw1 Part, a "BOM Sequence" field will appear containing a pick list which includes the sequence numbers of the Formula lines containing the selected Part. Using the Formula described in the previous sentence, the values in this BOM Sequence pick list would be 1 and 3. Once a BOM Sequence is selected, the "Quantity" field will populate with the required quantity for the selected BOM Sequence. Once "Apply" is clicked on the Inventory Final Staging form, only the BOM Sequence selected will have inventory staged. All remaining BOM Sequences for that Part will still need to be staged. Alternatively, if this flag is checked, selecting the Job number and Raw1 Part would force the "Quantity" field on the Inventory Final Staging form to populate with the total quantity required by the entire Formula rather than the quantity required by the first or third BOM Sequence of the Formula.

If checked, lot information is available to be printed on sales order report layouts and part forms, and job picklists, at any point in the staging process.

• Previously, lot information was only available after lots had passed through the last iteration of the final staging and the inventory was reserved.
• If unchecked, lot information for staged inventory will not be available on sales order report layouts, sales order part forms, and job picklists.

If checked, the user will only be able to issue the parts in the correct sequence to staging. This flag defaults to true.

• When unchecked, the user may issue lots to staging in any order, ignoring any required sequence/sequential values that are set.
• When issuing via WMS, if the "Type" field is set to "Job", the sequential BOM order will be enforced even if this flag is unchecked.

If checked, lots within Master Lots are available for pre-staging to Sales Orders via the Apply Inventory form when performing the Inventory > Pre-Staging transaction and selecting a Transaction Type of "Sales Orders" and a Type of "Staging."

• All lots within a Master Lot must be pre-staged at the same time. When selecting a specific lot within a Master Lot and performing the pre-stage transaction the system will pre-stage all lots within the Master Lot simultaneously.

Pick lists used to select up to five Sales Order/Purchase Order fields that will display in the calendar item that blocks off the time on the Dock Calendar when in weekly view.

• The "Bill-to PO" and "Ship-to PO" fields are only displayed for Sales Orders and Inter-Company Transfers; they will be blank for Purchase Orders.

Pick lists used to select up to three Sales Order/Purchase Order fields that will be used to sort the orders listed as available to schedule on the Dock Calendar.

Defines how many times per week cycle counting will be done.

• Typically, this field is set to 5, indicating cycle counting will occur 5 times per week.
• The more frequently the count is performed, the less parts in each count.
• The cycle counting concept is to count a few parts randomly on a daily basis to lessen the impact of a complete physical inventory on stockroom staff and the company.

Defines how often in the cycle counting plan the items classified as A through D will be counted.

• Cycle counting classifications are assigned to Parts using the "ABC" field on the Item Master General 1 tab.
• Example: Assigning a value of 1 in the "Weeks In Cycle A" field means each A item will be counted each week. A value of 4 means each A item would be counted once every four weeks.

Pick list used to set the default for the "Location Source" field on the Finish QC form, which indicates the Location in which material will be placed following completion of QC. Options are:

• Current - Material remains in its current Location and simply changes QC status.
• Default - Material is moved to its "Default Location" as defined on the Item Master General 1 tab.
• User-specified - Material is moved to the Location specified by the user on the Finish QC form.

Pick list used to determine if QC tests will be required by System or User Lot.

• Example: Assume this field is set to "System Lot". If a QC Group is added to a Part on the Item Master QC/Stability Tests tab, setting the "Frequency Type" and "Frequency" to "Every X Lots" and "3", respectively, indicates that QC testing for that Part will be performed on every 3 System Lots.

Pick list used to control what Quality Control Group should be used when moving a lot that was finished under an old BOM revision to QC Pending. Options are:

• Current - The Quality Control Group(s) on the current default BOM revision of the item being moved will be used.
• Previous - The Quality Control Group(s) on the BOM that was used to produce the lot being moved will be used.
• Prompt - Prompt the user asking if they want to use the previous QC tests or the current QC tests on the current revision or the one used on production (linked via re_revnum).

Pick list used to determine how the system will handle Lots previously marked At-Risk when failing QC results during production QC entry.

• All - All Lots used in the production of the At-Risk Lot being tested will be marked as failed if the At-Risk Lot being tested is marked as failed.
• Relieve - Only those Lots consumed when producing the At-Risk Lot being tested will be marked as failed if the At-Risk Lot being tested is failed.

Supports situations where the At-Risk feature is seen as too aggressive in failing all Lots used in the entire production process.

Example: Subassembly 10A is produced by consuming Lots of Raw Materials 20A and 20B. Finished Good 10B is produced by consuming Lots of Subassembly 10A. If this field is set to "Relieve" and 10B is failed during QC testing, then any Lots of 10A used to produce the 10B Lot being tested are marked as failed. If this field is set to "All" and the 10B Lot is marked as failed, then all Lots of 10A, 20A, and 20B used in the production of the 10B Lot being tested are marked as failed.

If checked, the system will prompt and require a user to enter their credentials before modifying/saving a Quality Control Group.

If checked, multiple users will be able to add QC values for the same job and QC Group on the Quality Control Results form in Production > Job Reporting

• Clicking the "Modify" button on the Quality Control Results form will be prevented if another user is currently modifying results.
• Added to support large jobs that extend over multiple days with many potential simultaneous process.

If checked, when a lot (with QC attached) has QC values entered and approved, if any other lower level lots have not had their qc results approved, the materials will be placed into an at risk status.

• Supports production scenarios where companies want to maintain an At-Risk status on production batches until the At-Risk status is cleared on the original consumed At-Risk material. (i.e. Raw Material or Sub Assembly)
• The process functions the same way as the existing at-risk process in the system, except that lots do not have to be finished into an at risk status to begin with. The lots will finish to qc pending(assuming qc attached) and if higher level qc results are entered first, the higher lots will then be marked at risk rather than completely approved. The lots will remain at risk until all levels of qc are completed. Failing QC results also works in the same manner, if any lower lots fail QC the same logic should be applied. All higher lots should also be changed to a failed qc status.

Memo field used to store an expression that specifies the Lot information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports, the "lc_Lotfld" variable must be added to the appropriate Job reports.
• The available fields for use in this text are: fi_prid, fi_quant (actually fi_balance), fi_group, fi_loid, fi_serial, fi_lotnum, fi_userlot, fi_orid, fi_attrib1, fi_attrib2, fi_attrib3, fi_descrip, fi_action, fi_lotdate, fi_expires, fi_catchwgt, fi_qc, fi_masterlot, fi_tally, fi_container, fi_contnum, lo_name, and lt_name.

Memo field used to store an expression that specifies the Job QC information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports the "lc_Qcinfo" variable must be added to the appropriate Job reports.
• lc_qcinfo should not be added in a Detail band.
• Example: q2_name + " " + STR(q2_min, 14, 4) + " " + q2_target + " " + STR(q2_max, 14, 4) + " " + q4_value + IIF(EMPTY(q2_notes), "", CHR(13) + " " + q2_notes) + "PASS1 PASS2".

Memo field used to store an expression that specifies the Job line information (the BOM items are formatted by the "FG BOM Text" field) to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports, the "lc_Fginfo" variable must be added to the appropriate Job reports.
• This variable lists the second Job line and the BOM items that go into it, then repeats for the next Job line, and continues for all remaining Job lines.
• Typically added to a Footer band in the batch ticket.
• The fields available to this expression are: lj_id, lj_linenum, lj_prid, lj_descrip, lj_quant, lj_reid, lj_ordnum, lj_orid, pr_codenum, pr_unid, pr_hazard, pr_jobmin, pr_jobquan, pr_psid, pr_unitwgt, pr_unitvol, pr_unitcub, pr_unitlen, pr_tarewgt, stockunit, ca_name, c2_name, p1_name, p2_name, p3_name, p4_name, p5_name.

Memo field used to store an expression that specifies Job line BOM information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports, the "lc_Fginfo" variable must be added to the appropriate Job reports.
• Typically added to a Footer band in the batch ticket.
• The fields available to this expression are: lj_quant, lj_linenum, lj_orid, lj_ordnum, lj_reid, sortfld, level, bocount, dispcnt, source, stockunit, stocktype, stockfactor, revunid, revwgt, revvol, revcub, revlen, parentid, orid, ljid, wanted, ordnum, prfact, b2_estcost, b2_boid, wgtcost, volcost, totwgt, totvol, totcub, totlen, wgtper, volper, required, exten, futext, bo_id, bo_bomfor, bo_prid, bo_seq, bo_notes, bo_desig, bo_reid, bo_subtot, bo_costonly, bo_unid, bo_scrap, bo_overage, bo_byproduct, bo_overissue, bo_bomcalc, bo_fixqty, pr_id, pr_codenum, pr_descrip, pr_level, pr_caid, pr_lispric, pr_stanlab, pr_stanmat, pr_stantot, pr_active, pr_unitwgt, pr_control, pr_stocked, pr_user1, pr_user2, pr_user3, pr_user4, pr_notes, pr_retail, pr_burden, pr_prunid, pr_scrap, pr_purpric, pr_c2id, pr_invchid, pr_unitvol, pr_unitcub, pr_hazard, pr_matbur, pr_fixstan, pr_fixmat, pr_fixlab, pr_fixbur, pr_fixmbur, pr_fixupdt, pr_hazflag, pr_stanfrt, pr_fixfrt, pr_futmat, pr_futlab, pr_futbur, pr_futmbur, pr_futfrt, pr_futstan, pr_unid, pr_orddays, pr_finback, pr_stanupdt, pr_futupdt, pr_overissue, pr_unitlen, pr_loid, pr_qclead, pr_tarewgt, un_name, un_type, un_factor, re_name, re_date, re_default, re_yield, re_lastrev, re_batyld, re_regulat, re_status, re_saved, re_unid, re_shid, ca_name, c2_name, p1_name, p2_name, p3_name, p4_name, p5_name.

Memo field used to store an expression that specifies the Routing information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports, the "lc_Routinfo" variable must be added to the appropriate Job reports.
• The available fields for use in this text are: lj_id, lj_linenum, lj_descrip, lj_quant,pr_id, pr_codenum, pr_descrip, un_name, as well as all fields from dtjob2, dmop, and dmcent.

Memo field used to store an expression that specifies the Job BOM Work Flow information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports, the "lc_trakinfo" variable must be added to the appropriate Job reports.
• The available fields for use in this text are: Item Master User Fields, BOM Revision User Fields, many of the t3_* and t2_* (t4_ fields show up as t2_ fields) fields, as well as username, assignedto, and disptime.
• Sample expression which provides the name of the work flow, who it is assigned to, and notes if they are present: ALLT(t2_name) + " | assigned to - " + assignedto + IIF(!EMPTY(t3_notes), CHR(13) + t3_notes + CHR(13), "")

Memo field used to store an expression that specifies the regulatory information to be displayed on Job documents.

• For the information and values within these fields to be displayed on reports the "lc_Regbom" variable must be added to the appropriate Job reports.
• The available fields for use in this text are: bo_prid, pr_codenum, pr_retail, pr_descrip, pr_stantot, pr_fixstan, pr_futstan, pr_unitwgt, pr_unitvol, pr_unitcub, pr_unitlen, pr_user1, pr_user2, pr_user3, pr_user4, prfact, un_name, un_type, srcbocount, srcwgtper, srcvolper, srctotwgt, srctotvol, srctotcub, srctotlen, srcquanper, srcexten, bocount, wgtper, volper, totwgt, totvol, totcub, totlen, quanper, exten, costper, lev, sortfld, bo_bomfor, and re_name.

Memo field used to store an expression for the "formula" Report Layout that will display the Quality Control Tests and QC specs required/associated with the selected Formula.

• Specifically, when printing the formula report, the system will evaluate this expression with all of the formula information available for each test in the QC specifications and generate a newline [CHR(13)] separated field lc_qctest that is available to the memory variables.
• Useful to show what the end goal of the formulation is.
• Note that QC results are sorted by q6_seq, then q2_seq.

If checked, the system will allow inventory issued to Master Lots to be included and available for selection when printing Job pick lists.

• Example: A company has a "racking" production Job where 20 trays are "racked" by using the Input Production function. Each finish on the "racking" Job represents one of the trays being added to the rack. During the finishing process for the job, users select a Master Lot in the "Master Lot" field. Once all 20 trays are racked, the company creates a "freeze dry" production Job to freeze dry these trays. At this point, the company needs to issue the Master Lots from the "racking" Job to the "freeze dry" Job. The "Include Master Lots in Picklists" flag enables this ability.

If checked, the word "None" will be printed anytime no results are returned when using table statements in Part Forms.

• If not checked, nothing will be printed when there are no results to be printed.

If checked, BOMs flagged as "Regulatory" will be summarized, specifically the bo_bomfor value will be '0'.

• If not checked, the bo_bomfor will display the right number.
• Unchecking this flag is useful when printing nutrition labels, where it is necessary that the bo_bomfor = pr_id to print the ingredients list.

When this box is checked, the system will only return QC Parent data on part forms for the lots that were relieved into the specific finish that created the lot that is being printed. If this box is unchecked, QC Parent data on part forms is returned for the entire job used to create the lot being printed.

Identifies the Part Form that will be used as the system default Safety Data Sheet (SDS).

• Individual items will use the system default as long as they are flagged with "Inherit System Part Forms" on their Item Master Properties tab, and are not overridden by part-specific or customer/part-specific forms, or forms in a Print Substitution Group.

Identifies the Part Form that will be used as the system default Certificate of Analysis (COA).

• Individual items will use the system default as long as they are flagged with "Inherit System Part Forms" on their Item Master Properties tab, and are not overridden by part-specific or customer/part-specific forms, or forms in a Print Substitution Group.

Defines the type of label and how it will be used in the system. Options are:

• Item Label
• Job Label
• Lot Label
• Master Lot Label
• PO Label
• Package Label
• SO Label

Search field used to select the desired Part Form.

Defines how the forms will print. Options are:

• By Line
• By Lot
• By Master Lot
• By Package
• By Quantity
• User Expression

The number of copies of the selected part form that will print.

Memo field used to store an expression the system will use to determine how the forms shall print.

• Only available when "Label Print Qty" is set to "User Expression".

Pick list used to determine if Lots are suggested when staging, issuing, or reserving. Options are:

• All - Lots are suggested for all Parts, regardless if they are Lot-controlled.
• Lot Required - Lots are suggested only for Parts that are Lot-controlled.
• None - The system will not make Lot suggestions. The word "System" will be listed in the "Lot" fields on the appropriate scanner functions.

If set to a value other than "None", the system will suggest the FEFO (First Expiration, First Out) Lot when reserving, issuing, and staging. If there is no expiration date, the system will suggest based on FIFO (First In, First Out) methodology.

Used for WMS only.

Pick list used to determine if Lots are suggested for picking based on Part Number or storage Location. Options are:

• Part - Suggests Lots by Part Number, regardless of where they are stored in a warehouse.
• Location - Suggests Lots by the lo_seq value of the Location of the Lot. Used for snake picking, which saves time and physical movement. Systematically, WMS will ask the server for all suggested Lots, remove already transacted Lots, then sort remaining Lots by lo_seq and suggest the first one. Note that if this setting is selected, the "Lots" button in the Reserve Sales Order WMS transaction will not be available unless users have the "WMS -- select lots when suggesting by location" security setting set to "Yes." The security was added for situations where a lot in the suggested Location does not have enough of the required materials and users will need to choose lots in a different Location.

Pick list used to determine if the Lot Chooser form in WMS (accessed via the "Lots" button) will filter down to the System Lot level or the User Lot level. Options are:

• While "System Lot" is the default selection, "User Lot" is useful in situations where a System Lot is not required, such as when scanning a GS1-128 barcode with Part and User Lot defined, or when adding custom Parts to Inter-Company Transfers.
• Used for WMS only.
• The WMS Application automatically disables the finder filter, on any lot chooser form, to a combobox and sets the value to System Lot if the item(s) selected is a catch weight or serialized part. This occurs even if the "Filter Lot Chooser" option in this field is set to "User Lot."

Pick list used to determine when the Lot Chooser form will be shown when issuing to Jobs via the Issue Job function on a WMS scanner. Options are:

• All - The Lot Chooser form will always be shown when the scanned criteria does not match a distinct Lot.
• Lot Control - The Lot Chooser form will always be shown for Lot controlled inventory under those circumstances, meaning the system cannot locate a distinct Lot number to choose automatically and/or more than one applicable Lot is found in the system. When inventory that is not lot controlled is scanned, the system will try to relive from that criteria until the required quantity is met.
• None - The Lot Chooser form will open when two Lots with the same Part/User Lot/System Lot number, but different Locations, exist.

Pick list used to define the default grouping on the Lot Chooser form in WMS, accessed via the issuing and reserving forms. Options are:

• Expiration Date
• Location
• Lot Date
• Master Lot
• Part Number
• System Lot
• User Lot

Pick list used to define how lots will be displayed when using the "Lots" button via WMS > Find Inventory. Options are:

• Expiration Date
• Location
• Lot Date
• Master Lot
• Part Number
• System Lot
• User Lot

Pick list used to set the default selection for the "Type" field on all WMS Lot finding forms. 

• Certain forms/transactions will not respect the default because in certain situations users will always want to pull from a certain bucket. Examples of these scenarios include de-issuing from a Job, un-reserving from a Sales Order, and Final Staging from staging.
• Used for WMS only.

Pick list used to set the default selection for the "QC Status" field on all WMS Lot finding forms. 

• Used for WMS only.

Pick list used to determine if the system will automatically select the Lot or if the user must manually select the Lot on the WMS Lot Chooser form if only one Lot is available for the selected Part.

• Useful if, when issuing to Jobs or reserving to Sales Orders in WMS, companies wish to have the user verify the Lot that will be chosen even if there is only one.
• If set to manual, a system lot will be required when moving lots in the WMS application.
• Used for WMS only.

Pick list used in conjunction with the "WMS -- Allow Issue Without Physical Scan" security setting to determine which barcodes may be scanned during the staging, issuing, and reserving functions. If the security setting is set to true, the value in this field is ignored. If set to false, it is respected. Options are:

• Any - Allows the user to scan any barcode type.
• Flat - Users are required to scan a flat barcode, such as 3 of 9 or code 128.
• Multi - Users are required to scan a 2D barcode, such as data matrix or GS1-128.

Pick list used to determine which piece of data is referenced when using an Application Identifier for a Part in a barcode. Options are:

• ID First - Indicates the AI is referencing the record ID number assigned to a Part when it was initially saved.
• Part Number First - Indicates the AI is referencing the "Part Number" assigned to the Item Master record.
• Retail Code First - Indicates the AI is referencing the "Retail Code" assigned to the Item Master General 1 tab.
• UPC First - Indicates the AI is referencing the UPC Number assigned to the Item Master UPC Numbers tab.
• Vendor Part First - Indicates the AI is referencing the "Part Number" assigned to a Vendor Part Cross Reference.

Pick list used to determine which piece of data is referenced when using an Application Identifier for a Location in a barcode.

Supports situations in which companies have Locations whose names exactly match record ID numbers. For example, a Location has a "Name" of "180" and a Location (the same or different one) has a record ID of "180". Options are:

• ID First - Indicates the AI is referencing the record ID number assigned to a Location when it was initially saved.
• Location Name First - Indicates the AI is referencing the "Name" assigned to the Location record.

Pick list used to determine how Lots are suggested when multiple Lots match the filter during reserving, issuing, and staging functions. Options are:

• Full - Lots with the largest quantity are suggested first.
• Smallest - Lots with the smallest quantity are suggested first.

Defines the maximum number of characters that can be displayed in any field/search box when sending data from the main Deacom application to the WMS application.

• Example: If a user were to perform a very wide open search using the Find Inventory function in WMS, the amount of records or data that would be passed to the scanner might exceed the memory limit on the scanner and cause issues. In most cases, users are trained to perform more relevant or smarter searches and issues like this will not generally arise.
• If companies have issues with large searches or large amounts of data being sent from the main application to the scanner, an appropriate value may be entered in this field.
• A general starting value is typically around 30,000.
• The minimum value in this field must be at least 30,000 in order to perform the save option.
• If using this field, the characters or records returned during a search may not represent the total amount of records that match the search criteria. Therefore, customers should use this option on a case-by-case basis and ensure users are trained to either perform smaller searches or be aware of the fact that search results will show limited results, which can then be used to further refine the search.
• Example: If a company has thousands of Raw Materials with Part Numbers from Raw1 through Raw30000, users might see search results stopping at Raw15000. In this case, users might begin another search with Raw15000 as the starting value in the search range.

Defines the number of seconds that, when typing into a "Location" search field on WMS, is used as the delay before returning results for the Locations filtered by the keys entered.

Defines the serial communications port to which the TIM1B controller is attached for shop floor labor data collection systems.

Pick list used to default the remember settings value to all print forms on WMS. When printing labels from WMS, instead of printing one form at a time, WMS now creates a grid for each label to print, where the quantities for each label are defaulted based on the selection in this field. Options are:

• Line - Populates the WMS print grid with the remembered values if labels for this line are printed again.
• Order - Populates the WMS print grid with the remembered values if labels for this order are printed again.
• Never

Defines the keycode on the scanner that will be used to initiate voice input/recognition. Options are: Custom Keycode, KEYCODE_BUTTON_L1, KEYCODE_BUTTON_L2, KEYCODE_BUTTON_R1, KEYCODE_BUTTON_R2, KEYCODE_PROG_YELLOW, and None.

• When selecting the "Customer Keycode" option, use the WMS Record Key field below to define the keycode.
• This same field exists on individual User records. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank.
• Supports the use of voice commands for menu navigation and button selection on scanners.

Defines the keycode on the scanner that will be used to initiate voice input/recognition. Options are: Custom Keycode, KEYCODE_BUTTON_L1, KEYCODE_BUTTON_L2, KEYCODE_BUTTON_R1, KEYCODE_BUTTON_R2, KEYCODE_PROG_YELLOW, and None.

• When selecting the "Customer Keycode" option, use the WMS Record Key field below to define the keycode.
• This same field exists on individual User records. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank.
• Supports the use of voice commands for menu navigation and button selection on scanners.

Option to set an on screen recording button in the WMS application. Options are Hide, None, and Show.

• The recording button initially displays in the top right corner but may be moved.
• Supports the ability to select buttons and navigate on the scanner when speaking a menu name or number.
• This same field exists on individual User records. The WMS application will evaluate the user setting first, then the settings in Inventory Options if the user setting is blank.
• Supports the use of voice commands for menu navigation, button selection, and button commands on scanners.
  • Voice input is available for the following button commands in Android WMS: 'Undo', 'Save', 'Exit', 'Continue', 'Next', 'Previous', 'Ok', 'Yes', 'No', 'Refresh', 'Print', 'Lines', 'Stage', 'Apply', 'Lots', 'Find', 'Details', 'Issue', 'All, 'Finish', 'Reserve', 'View', 'Quarantine', 'End Job', 'Back'

If checked, the "Use Entire Lots" flag in WMS will be checked by default.

• Additionally, if checked, the "Use Entire" field in the Reserve SO form is automatically set to "User Lot" when reserving on the scanner.

If checked, the system will automatically populate the Location information for the Lot selected when using the Reserve SO function in WMS.

• This will occur if only one Location exists in the Lot Chooser form on the scanner.
• Added to handle situations in which only one possible selection exists in the Lot Chooser form.
• Example: Assume users have a Part that exists in only one Location within a Lot. In this case, there is only one possible Location to choose from when reserving this Lot to a Sales Order in WMS.
• If this flag is checked, the need for the user to perform the extra step of selecting the only possible Location is removed.
• When using the WMS Reserve SO transaction and the user scans a barcode with AI 30 is 0 (Example: "(10)"+ ALLT(fi_userlot) + "(90)" + ALLT(UPPER(pr_codenum)) + "(30)0") , the setting for this flag determines the order that Qty and Location are presented to the user.
  • If this field is checked, the user is expected to first input a quantity, then press Enter to display the Lot Chooser form with the appropriate locations.
  • If this field is unchecked, the Lot Chooser with locations will be displayed immediately, at which point the user may enter/select a quantity.

If checked, inventory that is issued or reserved will no longer remain in a Master Lot after it has been issued or reserved to a Job or Sales Order.

• Useful if Lots will be de-issued from Jobs or Sales Orders at some point in the process.
• If not checked, users have to complete a two step de-issuing process, namely, de-issuing from the Job and then de-issuing from the Master Lot(s).
• If checked, the option to select "By Master Lot" in the "Label Print Quantity" field on the Edit Label form for SO labels will be disabled.

If checked, the scanner will skip fields that are populated and locate the first unpopulated field for the Physical Inventory function.

• If not checked, Deacom will go to the next field when "Enter" is pressed.
• Helps streamline the work required to complete a physical inventory.

If checked, Code 128 barcodes are treated as GS1-128 barcodes when scanned using WMS.

Pick list used to determine if the system will suggest the next Job or Sales Order upon opening an issue or reserve form in the WMS application only. Options are:

• Both - the system will suggest the next Job or Sales Order based on the "Planned Start" date (jo_planstart) or the "Due To Ship" date (to_dueship) and the Priority assigned to the Job or order, respectively.
• Jobs - upon opening an issue form on the scanner, the system will suggest the next Job based on the "Planned Start" date (jo_planstart) and the Priority assigned to the Job. The system will not suggest the next Sales Order when opening a reserve form.
• None - the system will not suggest the next Job or Sales Order when opening and issue or reserve form on the scanner.
• Sales Orders - upon opening a reserve form on the scanner, the system will suggest the next Sales Order based on the "Due To Ship" date (to_dueship) and the Priority assigned to the order. The system will not suggest the next Job when opening an issue form.

Additionally, if using the "Both," "Jobs," or "Sales Orders" options, the system will pre-fill future Jobs or Sales Orders respectively when no other older ones are available. The options in this field replace the need to scan from a pick list or manually input the Job/Sales Order number. 

If checked, the "Move Quantity" field on the Move Inventory form is defaulted to the Lot balance whenever the On Hand/Balance Quantity is updated or refreshed on the form.

• Applies to both the main application and WMS.
• This feature was added to provide users with another default value option other then "0" when a new Lot in selected on the Move Inventory form.

If checked, the system will use put away logic to suggest a suitable location for the inventory being received/moved.

• The suggested location will populate in the "Location" field of the form and the logic will re-run any time the quantity on the form is modified by the user.
• If not checked, there is no location suggestion and the user is free to choose a Location as desired.

If checked, the system will not display insufficient inventory prompts when issuing to jobs or reserving to sales orders in the WMS application.

• Applies to Reserve SO, Final Staging SO, Ship Sales Order, Issue Job, Final Staging Job, and Input Production transactions on the scanner.